Skip to content

Conversation

mariselo
Copy link
Contributor

@mariselo mariselo commented Oct 6, 2025

Clarify behavior of disabled pipelines regarding schedule triggers. This change in documentation is a repair item created from an incident in ADO: https://dev.azure.com/mseng/AzureDevOps/_workitems/edit/2238274

Clarify behavior of disabled pipelines regarding schedule triggers.
Repair item from ADO: https://dev.azure.com/mseng/AzureDevOps/_workitems/edit/2238274
@prmerger-automator
Copy link
Contributor

@mariselo : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

@prmerger-automator
Copy link
Contributor

@mariselo : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

@ttorble ttorble requested a review from Copilot October 6, 2025 15:19
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR updates the scheduled triggers documentation to clarify the behavior of disabled pipelines regarding schedule triggers. The change adds an important constraint that users need to be aware of when working with YAML pipeline schedules.

  • Added clarification that disabled pipelines don't automatically refresh schedule triggers when YAML changes are made

@ttorble
Copy link
Contributor

ttorble commented Oct 6, 2025

@steved0x

Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@steved0x
Copy link
Collaborator

#sign-off

@v-dirichards v-dirichards merged commit 5e16c8d into MicrosoftDocs:main Oct 14, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants